Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1928

reference
35-tree-1
name
1928
tree-preservation-order

undefined

35-tpo-1
uprn
address-text
point
POINT (-0.959820 50.865381)
geometry
MULTIPOLYGON (((-0.959763 50.865375,-0.959766 50.865386,-0.959774 50.865396,-0.959786 50.865404,-0.959802 50.865409,-0.959819 50.865411,-0.959837 50.865409,-0.959853 50.865404,-0.959865 50.865397,-0.959874 50.865387,-0.959877 50.865376,-0.959874 50.865364,-0.959866 50.865354,-0.959854 50.865346,-0.959838 50.865341,-0.959821 50.865339,-0.959803 50.865341,-0.959787 50.865346,-0.959774 50.865354,-0.959766 50.865363,-0.959763 50.865375)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL